Reception apparatus, transmission apparatus, and data processing method

ABSTRACT

A reception apparatus including reception circuitry and processing circuitry is provided. The reception circuitry is configured to receive control information and content, the control information including resource sharing information indicating whether a resource is shared among a plurality of applications. The processing circuitry is configured to control, based on the resource sharing information, sharing of the resource among the plurality of applications. The resource sharing information includes an identifier that is associated with the plurality of applications among which the resource is shared. The resource includes at least one file associated with at least one of the plurality of applications.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/766,850, filed Apr. 9, 2018, the entire contents of which isincorporated herein by reference. U.S. application Ser. No. 15/766,850is a National Stage of PCT/JP2016/083467, filed on Nov. 11, 2016, andclaims the benefit of priority under 35 U.S.C. § 119 of JapaneseApplication No. 2015-229769, filed Nov. 25, 2015.

TECHNICAL FIELD

The present technology relates to a reception apparatus, a transmissionapparatus, and a data processing method, and more particularly, to areception apparatus, a transmission apparatus, and a data processingmethod that permit sharing of a resource that is reused among aplurality of services.

BACKGROUND ART

In order to improve performance of access to files of an applicationaccompanying a specific service in a client apparatus, it is necessaryto cache necessary files in a local cache in advance.

ATSC (Advanced Television Systems Committee) 3.0, the United States'next generation of broadcasting standard currently under development,for example, assumes a model in which all files acquired viabroadcasting or communication are temporarily accumulated in a localcache on a local file system in a client apparatus and provided to astream renderer and an application. It should be noted, however, that afile system such as On Memory or SSD (Solid State Drive) or a specialdatabase is used as a local file system, for example.

These files in the local cache will be kept in the cache for a limitedtime period first and then deleted on the basis of parameters of cachecontrol headers of HTTP (Hypertext Transfer Protocol) headers thataccompany the files. It should be noted that such a process takes placewhere entity mode, a kind of ROUTE (Real-time Object Delivery overUnidirectional Transport) protocol delivery mode, is selected.

In general, all files in receivable broadcast waves cannot be cached dueto tuner and storage resource limitations of a client apparatus.Therefore, a type of operation is assumed in which only a group of filesrequired for a tuned service at that point are acquired and cached and,in a case where the service (channel) is switched over to other service,the storage resource is released immediately.

It should be noted that efforts are being made at a brisk pace todevelop and standardize technologies for delivering content such asbroadcast programs and advertisements from a broadcast server of abroadcasting station via unidirectional broadcasting or from acommunication server via bidirectional communication to a clientapparatus. As such a technology for realizing data delivery viabroadcasting or communication, the technology disclosed, for example, inPTL 1 is known.

CITATION LIST Patent Literature [PTL 1]

JP 2014-57227A

SUMMARY Technical Problem

Here, effective use of cash storage area, delivery band, and so on canbe achieved by sharing, for example, advertisement content files, filescommonly used in any service, of those files transported in a service.For this reason, proposals have been requested for sharing of resourcesthat are reused among a plurality of services.

The present technology has been devised in light of the abovecircumstances, and it is an object of the present technology to permitsharing of a resource that is reused among a plurality of services.

Solution to Problem

A reception apparatus of a first aspect of the present technology is areception apparatus that includes a reception section and a controlsection. The reception section receives content. The control sectioncontrols, on the basis of control information that is transportedtogether with the content and that includes resource sharing informationindicating whether a resource of the content is shared among a pluralityof services, storage of the resource in a storage apparatus such thatthe resource is shared among the plurality of services.

The reception apparatus of the first aspect of the present technologymay be a separate apparatus or an internal block making up an apparatus.Also, a data processing method of the first aspect of the presenttechnology is a data processing method associated with the receptionapparatus of the first aspect of the present technology described above.

In the reception apparatus and the data processing method of the firstaspect of the present technology, content is received, and storage ofthe resource in a storage apparatus is controlled on the basis ofcontrol information that is transported together with the content andthat includes resource sharing information indicating whether a resourceof the content is shared among a plurality of services such that theresource is shared among the plurality of services.

A transmission apparatus of a second aspect of the present technology isa transmission apparatus that includes a generation section and atransmission section. The generation section generates controlinformation that includes resource sharing information indicatingwhether a resource of content is shared among a plurality of services.The transmission section sends the control information together with thecontent.

The transmission apparatus of the second aspect of the presenttechnology may be a separate apparatus or an internal block making up anapparatus. Also, a data processing method of the second aspect of thepresent technology is a data processing method associated with thetransmission apparatus of the second aspect of the present technologydescribed above.

In the transmission apparatus and the data processing method of thesecond aspect of the present technology, control information isgenerated that includes resource sharing information indicating whethera resource of content is shared among a plurality of services, and thecontrol information is sent together with the content.

Advantageous Effect of Invention

According to the first and second aspects of the present technology, aresource that is reused by a plurality of services can be shared.

It should be noted that the effect described herein is not necessarilylimited and may be any one of the effects described in the presentdisclosure.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating a configuration of an embodiment of atransport system to which the present technology is applied.

FIG. 2 is a diagram illustrating an example of a protocol stack of an IPtransport scheme of the present technology.

FIG. 3 is a diagram illustrating a ROUTE/FLUTE structure.

FIG. 4 is a diagram illustrating a detailed ROUTE structure.

FIG. 5 is a diagram illustrating an overview of a cache quota domain.

FIG. 6 is a diagram illustrating arrangement of quota domainidentifiers.

FIG. 7 is a diagram illustrating a method of specifying quota domainidentifiers.

FIG. 8 is a diagram illustrating a relationship between quota domainidentifier specification and file cache.

FIG. 9 is a diagram illustrating a flow of advertisement insertion.

FIG. 10 is a diagram illustrating a flow of processes in an upper layeron a receiving side.

FIG. 11 is a diagram illustrating a description example of an xlink:hrefattribute of a Period element of MPD metadata.

FIG. 12 is a diagram describing chronological advertisement insertioncontrol using MPD metadata.

FIG. 13 is a diagram illustrating a description example of MPD metadata.

FIG. 14 is a diagram illustrating a description example of MPD metadata.

FIG. 15 is a diagram illustrating an example of an SLT format.

FIGS. 16-1 and 16-2 is a diagram illustrating an example of a USBDformat.

FIG. 17 is a diagram illustrating an example of an S-TSID format.

FIG. 18 is a diagram illustrating an example of an SrcFlow format.

FIG. 19 is a diagram illustrating an example of an AST format.

FIGS. 20-1 and 20-2 is a diagram illustrating an example of the ASTformat.

FIG. 21 is a diagram illustrating an example of the AST format.

FIG. 22 is a diagram illustrating a configuration example of an Ad/DASHserver.

FIG. 23 is a diagram illustrating a configuration example of a broadcastserver.

FIG. 24 is a diagram illustrating a configuration example of acommunication server.

FIG. 25 is a diagram illustrating a configuration example of a clientapparatus.

FIG. 26 is a flowchart describing a flow of processes on a transmittingside.

FIG. 27 is a flowchart describing a flow of processes on the receivingside.

FIG. 28 is a flowchart describing a flow of processes on the receivingside.

FIG. 29 is a diagram illustrating a configuration example of a computer.

DESCRIPTION OF EMBODIMENTS

A description will be given below of embodiments of the presenttechnology with reference to diagrams. It should be noted that adescription will be given in the following order.

1. System Configuration

2. Overview of Cache Quota Domain

3. Application Example of Application

4. Examples of Signaling

5. Configuration of Each Apparatus

6. Flow of Processes Performed by Each Apparatus

7. Modification Example

8. Configuration of Computer

1. System Configuration (Configuration of Transport System)

FIG. 1 is a diagram illustrating a configuration of an embodiment of atransport system to which the present technology is applied. It shouldbe noted that a system refers to a logical set of a plurality ofapparatuses.

In FIG. 1, a transport system 1 includes an Ad/DASH server 10, abroadcast server 20, a communication server 30, and a client apparatus40.

The Ad/DASH server 10 is a server for handling delivery service thatsupports MPEG-DASH (Dynamic Adaptive Streaming over HTTP). Here,MPEG-DASH is a streaming delivery standard compliant with OTT-V (OverThe Top Video) that relates to adaptive streaming delivery using HTTP(Hypertext Transfer Protocol)-based streaming protocol.

In this MPEG-DASH standard, a manifest file for describing metadata,management information of video and audio files and a file format fortransporting video content are specified. It should be noted that amanifest file, the former, is referred to as MPD (Media PresentationDescription). Also, a file format, the latter, is also referred to as asegment format.

The Ad/DASH server 10 generates files of a program content segment(hereinafter also referred to as a DASH segment) and an advertisementcontent segment (hereinafter also referred to as an Ad segment) andsends the files to the broadcast server 20 or the communication server30. Also, the Ad/DASH server 10 generates MPD metadata and sends it tothe broadcast server 20 or the communication server 30.

Also, the Ad/DASH server 10 generates an application and sends it to thebroadcast server 20 or the communication server 30. As this application,for example, a scrip application that can execute a script is included.It should be noted that applications developed using a markup languagesuch as HTML5 (HyperText Markup Language 5) and those developed using ascript language such as JavaScript (registered trademark) can be used asscript applications.

The broadcast server 20 is a transmitter capable of data transportcompliant with a digital broadcasting standard such as ATSC 3.0. Thebroadcast server 20 processes DASH segments, Ad segments, MPD metadata,and application files sent from the Ad/DASH server 10 and sends(broadcasts) them together with signaling via a transport channel 80.

Also, NRT content is input to the broadcast server 20. NRT content iscontent transported by NRT (Non Real Time) broadcasting and reproducedafter being stored temporarily in a storage of the client apparatus 40.The broadcast server 20 processes an NRT content file input thereto andsends (broadcasts) them via the transport channel 80.

The communication server 30 is a server that provides various pieces ofdata via the Internet 90 in response to a request from the clientapparatus 40 connected to the Internet 90. The communication server 30processes DASH segments, Ad segments, MPD metadata, and applicationfiles sent from the Ad/DASH server 10. Then, the communication server 30sends various files via the Internet 90 in response to a request fromthe client apparatus 40.

The client apparatus 40 is a receiver capable of receiving transporteddata compliant with a digital broadcasting standard such as ATSC 3.0.For example, the client apparatus 40 is a stationary receiver such astelevision receiver or set top box or a mobile receiver such assmartphone, mobile phone, or tablet computer. The client apparatus 40may be, for example, a piece of equipment mounted to an automobile suchas vehicle-mounted television.

The client apparatus 40 outputs images and sounds of content such asbroadcast programs and advertisements by receiving and processing filessuch as DASH segments, Ad segments, signaling, MPD metadata,applications, and NRT content sent (broadcast) from the broadcast server20 via the transport channel 80.

Also, in a case where equipped with a communication capability, theclient apparatus 40 can acquire various files by accessing thecommunication server 30 via the Internet 90. For example, the clientapparatus 40 outputs images and sounds of content such as VOD (Video OnDemand) programs and advertisements by receiving and processing filessuch as DASH segments, Ad segments, and MPD metadata sent (adaptivelydelivered by streaming) from the communication server 30 via theInternet 90.

It should be noted that, in the transport system 1, the transportchannel 80 may be not only terrestrial wave (terrestrial wavebroadcasting) but also satellite broadcasting using a broadcastingsatellite (BS) or communications satellite (CS) or wired broadcastingusing cables (CATV).

Also, ATSC 3.0 is a next-generation broadcasting standard in UnitedStates whose development is currently underway. ATSC 3.0 assumes thatmore advanced services will be provided by introducing, as a transportscheme, a scheme using IP (Internet Protocol) packet, used in the fieldof communication, for digital broadcasting (IP transport scheme) ratherthan MPEG2-TS (Transport Stream) scheme that is currently widespread.

(Protocol Stack of Present Technology)

FIG. 2 is a diagram illustrating an example of a protocol stack of theIP transport scheme of the present technology.

In FIG. 2, the lowermost layer is a physical layer. Digital broadcastingin IP transport scheme such as ATSC 3.0 not only handles transport usingunidirectional broadcasting but also transports some data by means ofbidirectional communication. In a case where broadcasting is used, thephysical layer thereof (broadcast) is associated with a broadcastingwave's frequency band assigned for services (channels).

A layer above the physical layer (broadcast) is an IP layer. The IPlayer corresponds to a network layer in a hierarchical communicationmodel. An IP packet is identified by an IP address. An upper layeradjacent to the IP layer is a UDP (User Datagram Protocol) layer thatcorresponds to a transport layer in the hierarchical communicationmodel, and the layer further thereabove is ROUTE (Real-time ObjectDelivery over Unidirectional Transport) or MMTP (MPEG Media TransportProtocol).

Also, the layer above the UDP layer, i.e., an IP packet including a UDPpacket, is transported with SLT metadata contained therein. SLS metadatais LLS (Link Layer Signaling) signaling that includes basic informationindicating a stream or service configuration in a broadcast network suchas information required for tuning to a service (tuning information). Itshould be noted that LLS signaling is signaling acquired ahead of SLS(Service Layer Signaling) signaling, and SLS signaling is acquired inaccordance with information included in LLS signaling.

ROUTE, a protocol for streaming file transfer, is an extended protocolof FLUTE (File Delivery over Unidirectional Transport). It should benoted that detailed content of ROUTE will be described later withreference to FIGS. 3 and 4.

Part of the upper layer adjacent to ROUTE is signaling (ROUTE specificSignaling) and NRT content (NRT Files). This signaling is SLS signalingand includes metadata such as USBD (User Service Bundle Description),S-TSID (Service-based Transport Session Instance Description), MPD(Media Presentation Description), AST (Application Signaling Table), andso on.

USD metadata includes information such as other metadata acquisitiondestination. S-TSID metadata, an extension of LSID (LCT Session InstanceDescription) for ATSC 3.0, is control information of the ROUTE protocol.MPD metadata is management information of video and audio filesdelivered by streaming as described earlier. AST is application controlinformation.

It should be noted that NRT content is an example of content transportedover a ROUTE session, and content such as application or electronicservice guide (ESG) may be, for example, transported over a ROUTEsession.

Of the upper layer adjacent to ROUTE, the layer other than thosedescribed above is DASH Segment (ISO BMFF). Also, the upper layeradjacent to the DASH Segment (ISO BMFF) is DASH Player/Decoders. Thatis, in a case where ROUTE is used as a transport protocol, stream dataof a service component (e.g., video, audio, subtitle) making up contentsuch as broadcast program is transported over a ROUTE session in unitsof a DASH Segment compliant with the ISO BMFF (ISO Base Media FileFormat) standard.

On the other hand, MMTP is a protocol for streaming file transfer. Partof the upper layer adjacent to MMTP is signaling (MMTP specificSignaling). Metadata such as USBD (User Service Bundle Description) andMPT (MMT Package Table) is included as this signaling.

Of the upper layers adjacent to MMTP, the layer other than signaling isMPU (Media Processing Unit) (ISO BMFF). Also, the upper layer adjacentto MPU (ISO BMFF) is DASH Player/Decoders. That is, in a case where MMTis used as a transport protocol, stream data of a service component(e.g., video, audio, subtitle) making up content such as broadcastprogram is transported over an MMTP session in units of an MPU compliantwith the ISO BMFF (ISO Base Media File Format) standard.

Thus, in the protocol stack depicted in FIG. 2, both ROUTE and MMTP arerepresented as a transport protocol. In unidirectionalbroadcasting-based streaming delivery, therefore, one of the twoprotocols, namely, ROUTE that transports a DASH Segment (ISO BMFF) fileor MMTP that transports an MPU (ISO BMFF) file, is used.

Also, in a case where bidirectional communication is used, the layerabove the physical layer (Broadband) is the IP layer that corresponds tothe network layer. Also, the upper layer adjacent to the IP layer is aTCP (Transmission Control Protocol) layer that corresponds to thetransport layer, and further, an upper layer adjacent to the TCP layeris an HTTP layer that corresponds to an application layer. That is,thanks to these layers, TCP/IP and other protocols working in networkssuch as the Internet 90 are implemented.

Part of the upper layer adjacent to the HTTP layer is signaling (AllSignaling Objects) and NRT content (NRT Files). This signaling includesall signaling such as signaling transported by ROUTE and MMTP describedabove. Also, NRT content is an example of content acquired viacommunication, and content such as application may be, for example,transported.

Of the upper layer adjacent to the HTTP layer, the layer other thanthose described above is DASH Segment (ISO BMFF). Further, the upperlayer adjacent to the DASH Segment (ISO BMFF) is DASH Player/Decoders.That is, in bidirectional communication-based streaming delivery, streamdata of a service component (e.g., video, audio, subtitle) making upcontent such as VOD program is transported in units of a DASH Segmentcompliant with the ISO BMFF standard.

Also, applications can be transported by using a unidirectionalbroadcasting protocol such as ROUTE or MMTP and a bidirectionalcommunication protocol such as TCP/IP. For example, these applicationscan be those developed with HTML5 or JS (JavaScript (registeredtrademark)).

It should be noted that, in FIG. 2, HTTP Proxy is written in part ofROUTE because, in the case of acquisition of a DASH Segment (ISO BMFF)file by an application, implementation is assumed in which broadcastmiddleware implemented in the client apparatus 40 behaves as an HTTPserver. Also, in FIG. 2, EME/CENC (Encrypted Media Extension/CommonEncryption Scheme) compliant with W3C (World Wide Web Consortium) andMPEG (Moving Picture Experts Group) is adopted as a security frameworkfor content protection. Therefore, EME/CENC is written in part of DASHSegment (ISO BMFF) and MPU (ISO BMFF).

Also, metadata including SLT metadata as LLS signaling and USBD, S-TSID,MPD, and AST as SLS signaling are written in a markup language such asXML (Extensible Markup Language).

As described above, in the protocol stack of the IP transport scheme ofthe present technology, unidirectional broadcasting-based layers andsome of bidirectional communication-based layers serve as a commonprotocol, allowing stream data of a service component making up contentto be transported through unidirectional broadcasting and bidirectionalcommunication in units of a DASH Segment compliant with the ISO BMFFstandard. For this reason, in a case where both unidirectionalbroadcasting-based streaming delivery and bidirectionalcommunication-based streaming delivery take place, implementation loadand processing load can be reduced, for example, in the broadcast server20 and the client apparatus 40 because the upper layer protocol has beencommonized.

(Route Structure)

FIG. 3 is a diagram illustrating a ROUTE structure. It should be noted,however, that, in FIG. 3, FLUTE is also written for comparison withROUTE.

FLUTE includes a scalable multicast protocol for file objects called ALC(Asynchronous Layered Coding), and specifically, it includes acombination of LCT (Layered Coding Transport) and FEC (Forward ErrorCorrection) components, building blocks of ALC.

Here, ALC is a protocol suited for unidirectional multicast transport ofan arbitrary binary file. That is, although developed as a highlyreliable asynchronous one-to-many broadcasting-based protocol, ALC usesLCT and FEC. As a result, a target file is subjected to FEC and placedinto an LCT packet, and where it is transported over IP multicast, it isplaced into a UDP packet and an IP packet.

FLUTE transport session is identified by a unique TSI (Transport SessionIdentifier) scoped by the sender's IP address. In FLUTE, the FEC schemecan be changed for each transport session or file. Also, FLUTE comeswith transport control information in XML format called FDT (FileDelivery Table) that is transported for each transport session.

A basic attribute and a transport control parameter of a target file arewritten in an FDT file to be transported over the same transport sessionas for an FEC encoding symbol contained in the LCT packet. FDT candefine mapping between a target file identifier and an LCT packet stringinto which corresponding FEC encoding symbol string has been placed andfurther store a MIME type and size, transport coding scheme, messagedigest, parameters required for FEC decoding, and so on for content ofeach file. It should be noted that FDT itself can be subjected to FECand that its own FEC parameters, for example, are transported separatelyover an LCT layer.

Incidentally, ROUTE is an extension of FLUTE, and object bundle andmedia-aware fragmentation can be cited as main differences therebetween.FIG. 4 illustrates a detailed ROUTE structure.

The ROUTE's object bundle is characterized in that it supports, at theprotocol level, a method of configuring a single super object bybundling together video and audio streams made up of source blocks ofdifferent sizes and generating an FEC repair stream based on the superobject and notification of a relationship between a source stream andthe repair stream.

In general, audio streams and the like are small in data amount (have asmall data object) per unit time. As a result, audio streams are smallerthan video streams in terms of source object size. Generating a repairsymbol for these streams having source objects of different sizes usingthe same FEC scheme for each stream results in different errorsensitivity depending on the magnitude of source object size.

ROUTE allows a super object to be configured by cutting out sourceblocks from source streams having different rates, thereby permitting arepair stream to be configured using an FEC repair symbol generated onthe basis of the super object. That is, a repair stream is generatedthat spans different kinds of source streams. Here, source streams madeup of source symbols and a repair stream made up of repair symbols canbe transported as different LCT sessions within a ROUTE session.

Information (control information) related to how an FEC stream isgenerated by configuring a super object from source blocks cut out froma plurality of source streams is written in S-TSID metadata, anextension of LSID (FDT). The receiving side can extract the target fileby reconstructing the super object from an LCT packet string transportedover the ROUTE session based on the information written in this S-TSIDmetadata.

In general, a broadcast stream is a model in which the transmitter sidemultiplexes and sends all streams making up a service and the receiverside selects streams required for the receiver itself. Therefore, theFEC configuration method realized by ROUTE is effective in a use casewhere a processing model of configuring a super object made up of allstreams making up a service on the transmitter side and reconstructingthe super object and selecting necessary streams on the receiving sideis applicable.

Hitherto, a description has been given of ROUTE, an extension of FLUTE.

2. Overview of Cache Quota Domain

Incidentally, in order to improve performance of access to applicationsaccompanying a specific service such as broadcast program in the clientapparatus 40, it is necessary to cache necessary files in a local cachein advance. For example, ATSC 3.0 assumes a model in which all filesacquired via broadcasting or communication are temporarily accumulatedin a local cache on a local file system of the client apparatus 40 andprovided to a stream renderer and an application.

Also, in the client apparatus 40, all files in receivable broadcastwaves cannot be cached due to tuner and storage resource limitations.Therefore, a type of operation is assumed in which only a group of filesrequired for a tuned service at that point are acquired and cached and,in a case where the service (channel) is switched over to other service,the storage resource is released immediately.

On the other hand, if, of those files transported in a service, anadvertisement content file, a file commonly used in all services, forexample, can be shared among a plurality of services, advantages can beoffered such as effective use of cache storage area and delivery band.For this reason, proposals have been requested for sharing of resourcesthat are reused among a plurality of services. The present technologyintroduces a cache quota domain concept, allowing for sharing ofresources reused among a plurality of services in the client apparatus40 by transporting a quota domain identifier for identifying a cachequota domain as signaling.

(Overview of Cache Quota Domain)

FIG. 5 is a diagram illustrating an overview of a cache quota domain.

A cache quota domain is a domain (group) for sharing reused resources.FIG. 5 illustrates a case in which service A, service B, and service Cbelong to quota domain 1, and service X and service Y belong to quotadomain 2. It should be noted that the storage area of the local cachedepicted in FIG. 5 is equivalent to that of a persistent cache 404B of alocal cache 404 depicted in FIG. 25 which will be described later.

In this case, applications, DASH Segments, and other files shared byservices A to C that belong to quota domain 1 are cached in the storagearea allocated to quota domain 1 of the local cache in the clientapparatus 40. That is, the files shared by the services that belong toquota domain 1 are cached in the storage area of the local cacheidentified by quota domain 1 (quota domain identifier thereof). As aresult, the files in the storage area in question can be acquired andprocessed (reproduced) in the services that belong to quota domain 1.

On the other hand, applications, DASH segments, period files, and otherfiles shared by services X and Y that belong to quota domain 2 arecached in the storage area allocated to quota domain 2 of the localcache. That is, the files shared by the services that belong to quotadomain 2 are cached in the storage area of the local cache identified byquota domain 2 (quota domain identifier thereof). As a result, the filesin the storage area in question can be acquired and processed(reproduced) in the services that belong to quota domain 2.

It should be noted, however, that each service cannot stretch beyond thequota domain to which it belongs to access resources of other quotadomain. For example, services A to C that belong to quota domain 1cannot access the resources of quota domain 2, and services X and Y thatbelong to quota domain 2 cannot access the resources of quota domain 1.

Thus, by introducing the cache quota domain concept, it is possible forthe services belonging to each quota domain to share and use (reuse) theresources available in the quota domain to which they belong.

For example, if a plurality of services provided by a singlebroadcasting station or a plurality of services provided by abroadcasting station alliance organized by a plurality of broadcastingstations can share resources (files) for each cache quota domain bybelonging to the same cache quota domain.

(Arrangement Example of Quota Domain Identifiers)

FIG. 6 is a diagram illustrating an arrangement example of quota domainidentifiers.

A quota domain identifier for identifying a cache quota domain can betransported by signaling that is transported by each layer of abroadcast wave. That is, by adding an attribute (or element) that canspecify a quota domain identifier of the cache quota domain to which atarget service belongs in signaling, it is possible to share a resource(file) among services that belong to the same cache quota domain basedon the quota domain identifier included in signaling in the clientapparatus 40.

As illustrated in FIG. 6, by extending SLT metadata, LLS signaling,contained in the payload of an IP/UDP packet, USBD metadata S-TSIDmetadata, or AST metadata, SLS signaling, contained in the payload of anIP/UDP packet and transported over an LCT session, a quota domainidentifier can be arranged therein.

(A) Arrangement in SLT Metadata

Where a quota domain identifier of a cache quota domain is specified byextending SLT metadata, SLT metadata can specify a plurality of serviceattributes. Therefore, an attribute (or element) that can specify thequota domain identifier is added as an attribute of a target service.Here, for example, the quota domain identifier of the cache quota domainto which a target service belongs can be specified by defining aquotaDomain attribute in a service element of SLT metadata.

For example, where services A to Z are provided, the quota domainidentifier of quota domain 1 (FIG. 5) is specified as the quotaDomainattribute of the service element for which a service ID of services A toC is specified in SLT metadata. Also, in this SLT metadata, the quotadomain identifier of quota domain 2 (FIG. 5) is specified as thequotaDomain attribute of the service element for which a service ID ofservices X and Y is specified.

Thus, it is possible to specify a quota domain identifier on aservice-by-service basis by defining the quotaDomain attribute in theservice element in SLT metadata.

(B) Arrangement in USBD Metadata

Where a quota domain identifier of a cache quota domain is specified byextending USBD metadata, the quota domain identifier of the cache quotadomain to which a target service belongs can be specified by definingthe quotaDomain attribute in a USD element of USBD metadata.

For example, where services A to Z are provided, the quota domainidentifier of quota domain 1 (FIG. 5) is specified as the quotaDomainattribute of the USD element in USBD metadata of services A to C. Also,for example, in USBD metadata of services X and Y, the quota domainidentifier of quota domain 2 (FIG. 5) is specified as the quotaDomainattribute of the USD element.

Thus, it is possible to specify a quota domain identifier on aservice-by-service basis by defining the quotaDomain attribute in theUSD element in USBD metadata.

(C) Arrangement in S-TSID Metadata

Where a quota domain identifier of a cache quota domain is specified byextending S-TSID metadata, the quota domain identifier of the cachequota domain to which a target LCT session belongs can be specified bydefining the quotaDomain attribute in a ContentInfo element of ansrcFlow element of an LS element of an RS element of S-TSID metadata.

Thus, it is possible to specify a quota domain identifier on anLCT-session-by-LCT-session basis by defining the quotaDomain attributein the ContentInfo element of the srcFlow element of the LS element ofthe RS element of S-TSID metadata.

(D) Arrangement in AST Metadata

Where a quota domain identifier of a cache quota domain is specified byextending AST metadata, the quota domain identifier of the cache quotadomain to which a target application belongs can be specified bydefining the quotaDomain attribute in an atsc:atscDescriptor element ofan applicationSpecificDescriptor element of an Application element ofAST metadata.

Thus, it is possible to specify a quota domain identifier on anapplication-by-application basis by defining the quotaDomain attributein the atsc:atscDescriptor element of the applicationSpecificDescriptorelement of the Application element of AST metadata.

As described above, by specifying a quota domain identifier by extendingSLT metadata, USBD metadata, S-TSID metadata, or AST metadata, it ispossible to share a resource (file) on a service-by-service, on anLCT-session-by-LCT-session, or on an application-by-application basiswithin the same cache quota domain.

That is, as illustrated in FIG. 7, each service includes one or aplurality of sessions, and a DASH segment or application file or anarbitrary file, for example, is transported over each LCT session.

Here, in a case where sharing of resources on a service-by-service basisis desired as depicted in FIG. 7, a quotaDomain attribute is defined byextending SLT metadata service entry (per-service basic attribute) orUSBD metadata's per-service attribute. That is, the quota domainidentifier for identifying a storage area of the local cache that storesfiles that are transported in a target service corresponds to thecharacter string specified by the quotaDomain attribute of SLT metadataor USBD metadata. It should be noted that files in this case are, forexample, files such as applications, DASH segments, or period files andinclude not only files acquired via broadcasting but also those acquiredvia communication.

It should be noted, however, that in a case where a cache quota domain(e.g., quota domain 1) is specified at the service level by thequotaDomain attribute of SLT metadata or USBD metadata, and where aninstruction is issued that all files transported over an LCT sessionthat belongs to a target service be cached in a local cache (persistentcache thereof), all the files are cached in the storage area allocatedto a cache quota domain (e.g., quota domain 1) of the local cache (A (B)in FIG. 8).

It should be noted that although details will be described later withreference to the SLT metadata format depicted in FIG. 15, SLS signalinglocation information is specified in the service element of SLTmetadata. Then, in a case where SLS signaling is acquired viabroadcasting, this location information is specified by aBroadcastSvcSignaling element. Where SLS signaling is acquired viacommunication, this location information is specified by an SvcInetUrlelement. For example, USBD metadata is acquired via broadcasting orcommunication in accordance with location information of the serviceelement of SLT metadata.

Also, in a case where sharing of resources on anLCT-session-by-LCT-session basis is desired as illustrated in FIG. 7, aquotaDomain attribute is defined by extending S-TSID metadata'sper-LCT-session attribute. That is, the quota domain identifier foridentifying a storage area of the local cache that stores files that aretransported over a target LCT session corresponds to the characterstring specified by the quotaDomain attribute of S-TSID metadata. Itshould be noted that files in this case are, for example, files such asapplications, DASH segments, or period files.

It should be noted, however, that in a case where a cache quota domain(e.g., quota domain 1) is specified at the LCT session level by thequotaDomain attribute of S-TSID metadata, it is recognized that theservice to which the target LCT session belongs to the cache quotadomain (e.g., quota domain 1).

Then, where an instruction is issued that files transported over an LCTsession whose cache quota domain (e.g., quota domain 1) has beenspecified be cached in a local cache (persistent cache thereof), thosefiles are cached in the storage area of a cache quota domain (e.g.,quota domain 1) of the local cache (C1 in FIG. 8). On the other hand,even when an LCT session belongs to the same service as the LCT sessionwhose cache quota domain (e.g., quota domain 1) has been specified, ifno cache quota domain is specified for that LCT session, files are notpersistently cached (C2 in FIG. 8).

It should be noted that although details will be described later withreference to the USBD metadata format depicted in FIG. 16, a URI(Uniform Resource Identifier) indicating an acquisition destination ofS-TSID metadata is specified in an STSIDUri attribute of the USD elementof USBD metadata. Then, S-TSID metadata is acquired in accordance withthis URI.

Also, where sharing of resources on an application-by-application basisis desired as illustrated in FIG. 7, a quotaDomain attribute is definedby extending AST metadata's per-application attribute. That is, thequota domain identifier for identifying a storage area of the localcache that stores files of an application to be written in target ASTmetadata corresponds to the character string specified by thequotaDomain attribute of AST metadata.

It should be noted, however, that where a cache quota domain (e.g.,quota domain 1) is specified at the application level by the quotaDomainattribute of AST metadata, it is recognized that the service to whichthe target application belongs belongs to the cache quota domain (e.g.,quota domain 1).

Then, where an instruction is issued that files of the application whosecache quota domain (e.g., quota domain 1) has been specified be cachedin a local cache (persistent cache thereof), those files are cached inthe storage area of a cache quota domain (e.g., quota domain 1) of thelocal cache (D in FIG. 8). On the other hand, even when an applicationbelongs to the same service as the application whose cache quota domain(e.g., quota domain 1) has been specified, if no cache quota domain isspecified for that application, files are not persistently cached.

Thus, by introducing the cache quota domain concept and transporting aquota domain identifier (resource sharing information) for identifying acache quota domain included in SLT, USBD, S-TSID, AST, or other metadata(control information), it is possible for the client apparatus 40 tohold a file (resource) included in services that belong to the samecache quota domain in a local cache (persistent cache thereof) and sharethe file (resource) on a service-by-service, LCT-session-by-LCT-session,or application-by-application basis.

3. Application Example of Application

A description will be given next of a case in which a cache quota domainis implemented in a system that inserts second content (advertisement)using an application transported together with first content (broadcastprogram) with reference to FIGS. 9 to 14. It should be noted that theapplication in question is designed to achieve ad-insertion control byexecuting a script. Therefore, the application will be hereinafterreferred to as a script app in the description given below.

(Flow of Advertisement Insertion)

FIG. 9 is a diagram illustrating a flow of advertisement insertion.

FIG. 9 depicts a case in which an advertisement (TV2_Ad) suited to theuser is inserted in place of a default advertisement (TV1_Ad) reproducedbetween broadcast programs (BP1, BP2) in the client apparatus 40.

In a case where the direction of time is from left to right in thefigure, an advertisement Ad1 acquired in realtime is normally reproducedfrom time t2 to time t3 between a time period from time t1 to time t2during which the broadcast program BP1 is reproduced and a time periodfrom time t3 to time t4 during which the broadcast program BP2 isreproduced.

Also, although two kinds of advertisements, namely, the defaultadvertisement Ad1 and the insertion advertisement Ad2, are available inthis example, the advertisement Ad2 is acquired via broadcasting orcommunication and cached in the local cache (persistent cache thereof)while a broadcast program BP1-1 is reproduced from time t1 to time t2,that is, timewise before an advertisement insertion interval.

In the client apparatus 40, when a scene of a broadcast program BP1-2appears, a question to the user is displayed superimposed on the image.Then, the client apparatus 40 displays an advertisement suited to theuser in question in response to the user's answer to the question. Inthe client apparatus 40, for example, where the user answers thequestion, the insertion advertisement Ad2 that matches the answer isread from the local cache (persistent cache thereof), and then thedefault advertisement Ad1 is replaced by the advertisement Ad2 suited tothe user.

Thus, by caching an advertisement that is more likely to be viewed bythe user in the local cache of the client apparatus 40 (persistent cachethereof), it is possible to display an advertisement suited to the userby using the cached advertisement.

It should be noted that although, in the example of advertisementinsertion depicted in FIG. 9, a case was depicted in which advertisementcontent suited to the user was selected in response to input operationof the user, advertisement content may be selected using information(e.g., sex, age, residential area) related to user characteristicsspecified in advance such as user preference or profile in addition tosuch exchange of information (interaction) with the user.

Incidentally, 3GPP (Third Generation Partnership Project) and DASH-IF(Industry Forum), standardization projects for mobile communicationsystem, follow the footsteps of an ad-insertion control realizationmethod personalized by Period element XLink that is prescribed byMPEG-DASH. It is assumed that ATSC 3.0 will also follow the footsteps ofthis ad-insertion control realization method. It should be noted thatXLink is a specification for defining a link between XML documents andadvised by W3C (World Wide Web Consortium).

This ad-insertion control adopts a method of making available a file foran MPD metadata advertisement insertion interval in advance anddynamically changing the Period element for specifying a segment for anadvertisement content stream in accordance with user characteristic(e.g., user preference). The client apparatus 40 that supports suchad-insertion control is depicted in FIG. 10.

In FIG. 10, the client apparatus 40 has an application/codec capability,a DASH client capability, and a transport stack/HTTP server capability.Also, the transport stack/HTTP server capability includes an XLinkresolver capability and an HTTP proxy cache capability. It should benoted, however, that the HTTP server of the communication server 30 mayhave the XLink resolver capability.

Here, in a case where MPD metadata to be transported as SLS signaling isreceived by the client apparatus 40, the MPD metadata is acquired by anHTTP proxy cache, and then the DASH client is notified (S51). In thisMPD metadata, a URL (Uniform Resource Locator) is specified that is tobe resolved by the XLink resolver that runs on the HTTP server of theclient apparatus 40 or the communication server 30 as an xlink:hrefattribute of the Period element.

Specifically, focusing attention to the Period element, of A1 (Ad Break#1), M1 (Main Program), A2 (Ad Break #2), M2 (Main Program), A3 (AdBreak #3), and M3 (Main Program), the Period elements written in MPDmetadata, as illustrated in FIG. 11,“http://adservice.com/adp-1?user=$groupID$” is written as an xlink:hrefattribute URL.

It should be noted that “http://adservice.com/adp-1?user=$groupID$” isalso written as an xlink:href attribute URL in A2 (Ad Break #2) or A3(Ad Break #3) and that the URL is processed similarly to A1 (Ad Break#1).

Referring back to the description of FIG. 10, in the client apparatus40, an HTTP request is issued to the XLink resolver on the HTTP serverof the client apparatus 40 or the communication server 30 by inserting avalue identifying the user in the parameter portion of the groupID ofthis URL (S52). For example, a URL with a groupID value inserted thereinsuch as “http://adservice.com/adp-1?user=classA” is notified to theXLink resolver.

When the URL with a groupID value inserted therein is notified from theDASH client, the XLink resolver of the client apparatus 40 or thecommunication server 30 returns, to the DASH client, a Period elementfile (hereinafter referred to as a period file) including a URLgenerated for a specific user (e.g., classA user) identified by thegroupID (S53). The URL included in this Period element is a URL of asegment (segment URL) delivered using the ROUTE protocol in the case ofdelivery via unidirectional broadcasting and using the HTTP protocol inthe case of delivery via bidirectional communication.

Then, in the client apparatus 40, the DASH client and the HTTP proxycache engage in interaction such as requesting and delivering a segmentin accordance with the Period element of the period file acquired by theprocess in step S53. As a result, a segment that matches the segment URLof the Period element is acquired (S54).

Advertisement content that matches the segment acquired in this manneris reproduced during the advertisement insertion interval (e.g.,interval from time t2 to time t3 in FIG. 9).

More specifically, FIG. 12 illustrates ad-insertion control that insertsA1 (Ad Break #1) timewise before M1 reproduction, inserts A2 (Ad Break#2) between M1 and M2, and inserts A3 (Ad Break #3) between M2 and M3where M1 (Main Program) is reproduced from 00:00:00 to 00:15:00, M2(Main Program) is reproduced from 00:15:00 to 00:30:00, and M3 (MainProgram) is reproduced from 00:30:00 to 00:42:00.

In this example, three kinds of advertisements are available as A1 (AdBreak #1), and the content of advertisement to be reproduced changesdynamically in accordance with the user characteristic (e.g., userpreference) such as male in his 30s or female in her 60s. Similarly, aplurality of advertisements are available as A2 (Ad Break #2) and A3 (AdBreak #3), allowing an advertisement that matches the usercharacteristic to be reproduced.

It should be noted that although, in FIG. 10, an example was describedin which the XLink resolver ran on the HTTP server of the clientapparatus 40 or the communication server 30, a script application canplay a role of the XLink resolver in the client apparatus 40.

That is, where the DASH client detects a URL of an xlink:href attributeof the Period element for advertisement insertion by parsing (analyzingthe syntax of) MPD metadata, the URL thereof is notified to the scriptapplication rather than immediately sending an HTTP request to the XLinkresolver running on the HTTP server.

When the URL is notified from the DASH client (when XLink resolution isrequested), the script application selects, of pieces of possibleadvertisement content (Ad segments) for insertion for that interval, theone suited to the target user (Ad segment), on the basis of informationfor identifying an advertisement insertion interval reflected in thepath portion or query character string of the URL.

Then, the script application generates a period file including thePeriod element appropriate to the selected piece of advertisementcontent (Ad segment) and replies to the DASH client. For example, thePeriod element of this period file includes the URL generated for aspecific user (e.g., classA user) specified by the groupID, and when agroup of Ad segments are reproduced, the advertisement content isreproduced, on the basis of the list of the segment URL.

Here, as for the selection of advertisement content suited to the user,for example, the selection may be made in some cases in accordance withuser preferences managed by the client apparatus 40 or in other cases inaccordance with information acquired as required as a result of exchangeof information (interaction) with the user. For example, in the case ofadvertisement insertion depicted in FIG. 9 described above,advertisement content suited to the user is selected in accordance withuser input operation.

Thus, resolving XLink of the Period element of MPD metadata on the sideof the client apparatus 40 eliminates the need to request XLinkresolution to the XLink resolver that runs on the HTTP server of thecommunication server 30.

For this reason, in a case where XLink is revolved by the XLink resolverof the communication server 30, concentration of access to thecommunication server 30 from a number of client apparatuses 40 connectedto the Internet 90 is expected immediately before the advertisementinsertion interval. However, XLink resolution using the XLink resolverof the client apparatus 40 eliminates increase in transaction processingload for XLink resolution.

Also, in the client apparatus 40, it is possible to ensure reliabilityof advertisement insertion through ad-insertion control by cachingpieces of possible advertisement content (Ad segments), acquired viabroadcasting or communication, in the local cache (persistent cachethereof) timewise before the advertisement insertion interval. Forexample, in a case where advertisement content (Ad segment) is acquiredvia communication, there is a possibility that advertisement content (Adsegments) may not be acquired depending on the communication conditionof the Internet 90 and so on. However, caching advertisement content (Adsegments) in advance contributes to more reliable advertisementinsertion through ad-insertion control.

Further, the present technology introduces the cache quota domainconcept, allowing for sharing of an advertisement content (Ad segment)file reused among a plurality of services in the client apparatus 40.This contributes to improved reusability of possible advertisementcontent (Ad segment) cached in the local cache (persistent cachethereof), allowing for more reliable advertisement insertion throughad-insertion control.

(MPD Description Examples)

A description will be given next of description examples of MPD metadatain XML format with reference to FIGS. 13 and 14.

It should be noted that the Period element, an AdaptationSet element,and a Representation element are written in hierarchical structure inMPD metadata. The Period element serves as a unit of writing aconfiguration of a service such as content. Also, the AdaptationSetelement and the Representation element are used for each servicecomponent stream such as video, audio, subtitle, and so on and permitwriting of respective stream attributes of these elements.

In the description example of MPD metadata depicted in FIG. 13, thePeriod element of a main program and the Period element of anadvertisement (Ad) are written.

Information for managing reproduction of the main program content (videofile in MP4 format) is written in the Period element of the mainprogram. It should be noted, however, that an ID corresponding to theEIDR (Entertainment Identifier Registry) is assigned to a schemeIdUriattribute and a value attribute of an AssetIdentifier element.

In the Period element of the advertisement (Ad), on the other hand, aURL is written in the xlink:href attribute of the Period element (A inFIG. 13) together with information for managing reproduction of thedefault advertisement content (video file in MP4 format). This URL isnotified to the XLink resolver that runs on the HTTP server of thecommunication server 30, allowing acquisition of an advertisement forinsertion and replacement of the default advertisement with theadvertisement for insertion.

In the metadata description example depicted in FIG. 14, the Periodelement of a main program and the Period element of an advertisement(Ad) are written.

Information for managing reproduction of the main program content (videofile in MP4 format) is written in the Period element of the mainprogram.

In the Period element of the advertisement (Ad), on the other hand, aURL is written in the xlink:href attribute of the Period element (A inFIG. 14) together with information for managing reproduction of thedefault advertisement content (video file in MP4 format). Here, a URLhaving a groupID value inserted therein is notified to the XLinkresolver that runs on the HTTP server of the client apparatus 40,allowing acquisition of an advertisement suited to a specific user andreplacement of the default advertisement with the advertisement suitedto the user. It should be noted that “urn:atsc:ad-insertion” in A ofFIG. 14 indicates that a request must be made to the script (scriptapplication) executed locally (by the client apparatus 40) to resolvead-insertion control and that details thereof will be described later.

It should be noted that although sharing of an advertisement content (Adsegment) file among a plurality of services using a cache quota domainwas described above by citing advertisement content as an example, thepresent technology is also applicable to other content in addition toadvertisement. Also, a file is merely an example of a content resource,and any kind of data can be used as long as it can be processed by theclient apparatus 40.

4. Examples of Signaling

A description will be given next of an example of a signaling format fortransporting a quota domain identifier for identifying a cache quotadomain with reference to FIGS. 15 to 21.

(SLT Format)

FIG. 15 is a diagram illustrating an example of an SLT metadata formatin XML format. It should be noted that, of the elements and attributesin FIG. 15, the attributes are marked with “@.” Also, the indentedelements and attributes are specified for their upper element. Theserelationships are similarly to other signaling formats which will bedescribed later.

An SLT element is a root element and is an upper element of a bsidattribute, an sltCapabilities attribute, an sltInetUrl element, and aService element.

A broadcast stream ID is specified in the bsid attribute. Informationrelated to necessary capabilities is specified in the sltCapabilitiesattribute.

A base URL for acquiring ESG or SLS signaling is specified in thesltInetUrl element. The sltInetUrl element is an upper element of aurlType attribute. A file type that can be used for the base URL isspecified in the urlType attribute.

Information related to one or a plurality of services is specified inthe Service element. The Service element is an upper element of aserviceId attribute, an sltSvcSeqNum attribute, a protected attribute, amajorChannelNo attribute, a minorChannelNo attribute, a serviceCategoryattribute, a shortServiceName attribute, a hidden attribute, abroadbandAccessRequired attribute, an svcCapabilities attribute, aquotaDomain attribute, a BroadcastSvcSignaling element, and ansvcInetUrl element.

A service ID is specified in the serviceId attribute. Informationrelated to SLT metadata version is specified in the sltSvcSeqNumattribute. Encryption information indicating service protection isspecified in the protected attribute.

A major channel number is specified in the majorChannelNo attribute. Aminor channel number is specified in the minorChannelNo attribute. Aservice category is specified in the serviceCategory attribute. A shortservice name is specified in the shortServiceName attribute.

Whether a service is a hidden service is specified in the hiddenattribute. Whether it is necessary to access a communication circuitsuch as the Internet 90 is specified in the broadbandAccessRequiredattribute. Information related to necessary capabilities for decoding isspecified in the svcCapabilities attribute.

A quota domain identifier of a cache quota domain to which a targetservice belongs is specified in the quotaDomain attribute. A resource(file) cached in the local memory is shared among services that belongto the same cache quota domain.

Information related to SLS signaling acquisition destination where theSLS signaling is acquired via broadcasting is specified in theBroadcastSvcSignaling element. The BroadcastSvcSignaling element is anupper element of an slsProtocol attribute, an slsMajorProtocolVersionattribute, an slsMinorProtocolVersion attribute, an slsPlpId attribute,an slsDestinationIpAddress attribute, an slsDestinationUdpPortattribute, and an slsSourceIpAddress attribute.

Information related to SLS signaling protocol is specified in theslsProtocol attribute. A major version number of an SLS signalingprotocol is specified in the slsMajorProtocolVersion attribute. A minorversion number of an SLS signaling protocol is specified in theslsMinorProtocolVersion attribute.

An ID of a PLP (Physical Layer Pipe) over which SLS signaling istransported is specified in the slsPlpId attribute. An IP address of anSLS signaling destination is specified in the slsDestinationIpAddressattribute. A port number of an SLS signaling destination is specified inthe slsDestinationUdpPort attribute. An IP address of an SLS signalingsource is specified in the slsSourceIpAddress attribute.

A URL of an SLS signaling acquisition destination is specified in thesvcInetUrl element where SLS signaling is acquired via communication.The svcInetUrl element is an upper element of a urlType attribute. Afile type that can be used for this URL is specified in the urlTypeattribute.

It should be noted that, as for the number of occurrences (Use) in FIG.15, where “1” is specified, the element or the attribute is alwaysspecified only once, and that where “0 . . . 1” is specified, it isoptional to specify the element or the attribute. Also, where “1 . . .N” is specified, the element or the attribute is specified once or more,and where “0 . . . N” is specified, it is optional to specify theelement or the attribute once or more.

Also, where “unsignedShort” or “unsignedByte” is specified as Data Type,it indicates that the value of the element or the attribute is ofinteger type. Where “string” is specified as Data Type, it indicatesthat the value of the element or the attribute is of character stringtype. Where “anyURT” is specified, it indicates that the value of theelement or the attribute is a character string in URI format. Where“boolean” is specified as Data Type, it indicates that the value of theelement or the attribute is of Boolean type. It should be noted thatwhere “language” is specified as Data Type, it indicates that the valueof the element or the attribute is valid as a value of an xml:langattribute. Where “dateTime” is specified, it indicates that the value ofthe element or the attribute indicates a specific date and time.

(USBD Format)

FIG. 16 is a diagram illustrating an example of a USBD metadata in XMLformat.

A bundleDescription element is a root element and is an upper element ofa userServiceDescription element (USD element). ThisuserServiceDescription element is an upper element of a globalServiceIDattribute, a serviceId attribute, a serviceStatus attribute, afullMPDUri attribute, an sTSIDUri attribute, a quotaDomain attribute, aname element, a serviceLanguage element, a capabilityCode element, and adeliveryMethod element.

A global service ID is specified in the globalServiceID attribute. Aservice ID is specified in the serviceId attribute. Information relatedto service status is specified in the serviceStatus attribute. A URI forreferring to MPD metadata is specified in the fullMPDUri attribute. AURI for referring to S-TSID metadata is specified in the sTSIDUriattribute.

A quota domain identifier of a cache quota domain to which a targetservice belongs is specified in the quotaDomain attribute. Services thatbelong to the same cache quota domain share a resource (file) cached inthe local memory.

A name of an ATSC 3.0 service is specified in the name element. The nameelement is an upper element of a lang attribute. A language of an ATSC3.0 service name is specified in the lang attribute. A language that canbe used in an ATSC 3.0 service is specified in the serviceLanguageelement. A code relating to a capability is specified in thecapabilityCode element.

Information related to a data delivery method is specified in thedeliveryMethod element. The deliveryMethod element is an upper elementof a broadcastAppService element and a unicastAppService element. ThebroadcastAppService element is an upper element of a basePatternelement, and information related to delivery via broadcasting isspecified in the broadcastAppService element. The unicastAppServiceelement is an upper element of the basePattern element, and informationrelated to delivery via communication is specified in theunicastAppService element.

(S-TSID Format)

FIG. 17 is a diagram illustrating an example of an S-TSID metadataformat.

An S-TSID element is a root element and is an upper element of theserviceId attribute and the RS element. A service ID is specified in theserviceId attribute.

Information related to ROUTE session is specified in the RS element. TheRS element is an upper element of the bsid attribute, an sIpAddrattribute, a dIpAddr attribute, a dport attribute, a PLPID attribute,and an LS element.

A broadcast stream ID is specified in the bsid attribute. A source IPaddress is specified in the sIpAddr attribute. A destination IP addressis specified in the dIpAddr attribute. A destination port number isspecified in the dport attribute. A ROUTE session PLP ID is specified inthe PLPID attribute.

Information related to LCT session is specified in the LS element. TheLS element is an upper element of a tsi attribute, a PLPID attribute, abw attribute, a startTime attribute, an endTime attribute, an SrcFlowelement, and an RprFlow element.

A TSI is specified in the tsi attribute. A PLP ID is specified in thePLPID attribute. A bandwidth is specified in the bw attribute. A startdate and time and an end date and time are specified respectively in thestartTime attribute and the endTime attribute. Source flow informationis specified in the SrcFlow element. It should be noted that thedetailed content of this SrcFlow element will be described later withreference to FIG. 18. Repair flow information is specified in theRprFlow element.

(SrcFlow Element Format)

FIG. 18 is a diagram illustrating an example of format of the SrcFlowelement included in the S-TSID metadata depicted in FIG. 17.

The SrcFlow element is an upper element of an rt attribute, aminBuffSize attribute, an EFDT element, a ContentInfo element, and aPayload element. A minimum buffer size required for the client apparatus40 is specified in the minBuffSize attribute.

Information related to an extended FDT is specified in the EFDT element.Information related to content is specified in the ContentInfo element.The ContentInfo element is an upper element of the quotaDomainattribute.

A quota domain identifier of a cache quota domain to which a serviceincluding a target LCT session belongs is specified in the quotaDomainattribute. A resource (file) cached in the local memory is shared amongservices that belong to the same cache quota domain.

The Payload element is an upper element of a codePoint attribute, aformatID attribute, a frag attribute, an order attribute, ansrcFecPayloadID attribute, and an FECParams attribute, and informationrelated to a payload of a ROUTE packet contained in a source flow objectis specified in the Payload element.

(AST Format)

FIGS. 19 to 21 are diagrams illustrating examples of AST metadataformats.

An ApplicationList element is a root element and is an upper element ofthe Application element and an ApplicationReference element.

Information related to application is specified in the Applicationelement. The Application element is an upper element of an appNameelement, an applicationIdentifier element, an applicationDescriptorelement, an applicationUsageDescriptor element, an applicationBoundaryelement, an applicationTransport element, an applicationLocationelement, and an applicationSpecificDescriptor element.

The appName element is an upper element of a Language attribute, and anapplication name is specified in the appName element. TheapplicationIdentifier element is an upper element of an orgID elementand an appID element, and an application ID of an application isspecified in the applicationIdentifier element.

The applicationDescriptor element is an upper element of a type element,a controlCode element, a visibility element, a serviceBound element, apriority element, a version element, an icon element, and astorageCapabilities element, and information related to targetapplication property is specified.

The applicationUsageDescriptor element is an upper element of anApplicationUsage element, and information related to application usagetype is specified. Information related to application boundary isspecified in the applicationBoundary element. Information related toapplication transport protocol is specified in the applicationTransportelement.

In the case of HTTP transport type, a URLBase element and a URLExtensionelement are provided, and a URL is specified. An extended URL isspecified in the URLExtension element. In addition, in the case of ROUTEtransport type, an atsc:ROUTESessionInfo element (including anLCTSession element, a tsi attribute, and a plpID attribute), abroadcastStreamId attribute, a plpID attribute, a sourceIpAddressattribute, a destinationIpAddress attribute, and a destinationPortattribute are provided, and information related to ROUTE session isspecified.

Application location information is specified in the applicationLocationelement. An application descriptor is provided in theapplicationSpecificDescriptor element. As this descriptor, dvbDescriptorcorresponding to DVB (Digital Video Broadcasting), htmlDescriptorcorresponding to HTML (HyperText Markup Language), atscDescriptorcorresponding to ATSC, or otherDescriptor corresponding to otherstandard is selectively provided.

The atsc:atscDescriptor element is an upper element of a quotaDomainattribute, a size element, a requiredCapabilities element, an iconelement, an ApplicationRecordingDescriptor element, a timeSlotInfoelement, a contentLinkage element, a contentItem element, and agraphicConstraintsDescriptor, and information related to ATSC (ATSC 3.0)is specified.

A quota domain identifier of a cache quota domain to which a serviceincluding a target application belongs is specified in the quotaDomainattribute. A resource (file) cached in the local memory is shared amongservices that belong to the same cache quota domain.

It should be noted, however, that the icon element includes a filenameattribute, a size attribute, and an aspectRatio attribute. Also, theApplicationRecordingDescriptor element includes ascheduled_recording_flag element, a trick_mode_aware_flag element, atime_shift_flag element, a dynamic_flag element, an av_synced_flagelement, an initiating_replay_flag element, and a storage_propertieselement. Further, a timeSlotInfo element includes a timeslot_typeelement, a timeslot start element, a timeslot_length element, anacquisition_time element, and a repeat_period element.

Also, the contentItem element includes a location attribute, acontentLinkage attribute, an updatesAvailable attribute, the sizeattribute, and the timeSlotInfo element. This timeSlotInfo elementincludes the timeslot_type element, the timeslot start element, thetimeslot_length element, the acquisition_time element, and therepeat_period element. The graphicConstraintsDescriptor element includesa can_run_without_visible_ui element, a handles_configuration_changedelement, a handles_externally_controlledvideo element, agraphics_configuration_byte element, and a screenPosition element.

It should be noted that the formats, as described with reference toFIGS. 15 to 21, of SLT metadata, USBD metadata, S-TSID metadata, and ASTmetadata are merely examples, and formats partially changed, forexample, by adding other elements and attributes may be used. Also, SLTmetadata, USBD metadata, S-TSID metadata, and AST metadata are notlimited to XML format and may be written in other markup language or maybe in section format.

Also, a quota domain identifier specified by the quotaDomain attributeadded by extending signaling of SLT metadata, USBD metadata, S-TSIDmetadata, AST metadata, and so on may be included in one kind ofmetadata or in a plurality of kinds of metadata. Also, in a case where aplurality of services are provided, the quota domain identifierspecified by the quotaDomain attribute is written in different kinds ofmetadata, one kind for each service. Further, although, in each of themetadata format examples described above, an example was described inwhich a quota domain identifier was specified by the quotaDomainattribute, a quota domain identifier is not necessarily specified by anattribute and may be specified, for example, by an element orinformation written as text.

5. Configuration of Each Apparatus

A description will be given next of configurations of the Ad/DASH server10, the broadcast server 20, the communication server 30, and the clientapparatus 40 on the receiving side in the transport system 1 depicted inFIG. 1 with reference to FIGS. 22 to 25.

(Configuration of Ad/DASH Server)

FIG. 22 is a diagram illustrating a configuration example of the Ad/DASHserver 10 depicted in FIG. 1.

In FIG. 22, the Ad/DASH server 10 includes a reception section 101, anAd/DASH segment generation section 102, a script application generationsection 103, an MPD generation section 104, a processing section 105,and a transmission section 106.

The reception section 101 receives streaming delivery data, for example,from an external server (not depicted) and supplies data to the Ad/DASHsegment generation section 102, the script application generationsection 103, and the MPD generation section 104.

The Ad/DASH segment generation section 102 generates an Ad segment and aDASH segment based on data supplied from the reception section 101 andsupplies the segments to the processing section 105.

Here, the Ad segment is a segment file acquired by processingadvertisement content. Also, the DASH segment is a segment file acquiredby processing live content (e.g., live programs such as on-the-spotsports broadcasting) sent via a transport channel or a communicationcircuit from a broadcasting site or recorded content accumulated in thestorage (e.g., prerecorded programs such as dramas). It can be said thatan Ad segment is also a kind of DASH segment. However, a descriptionwill be given by differentiating between Ad segment and DASH segment forreasons of description.

The script application generation section 103 generates a scriptapplication based on the data supplied from the reception section 101and supplies the data to the processing section 105. Here, the scriptapplication is an application that can execute a script. This scriptapplication can be an application developed using a markup language suchas HTML5 or an application developed using a script language such asJavaScript (registered trademark).

The MPD generation section 104 generates MPD metadata based on the datasupplied from the reception section 101 and supplies the MPD metadata tothe processing section 105. Here, although the Period elementappropriate to content such as program or advertisement is written inMPD metadata, the detailed content thereof will be described later.

The processing section 105 performs necessary processes on the Adsegment and the DASH segment supplied from the Ad/DASH segmentgeneration section 102, the script application supplied from the scriptapplication generation section 103, and the MPD metadata supplied fromthe MPD generation section 104 and supplies the data to the transmissionsection 106.

The transmission section 106 sends the data supplied from the processingsection 105 to the broadcast server 20 or the communication server 30.It should be noted that, here, of the data (files) of the Ad segment andthe DASH segment, the script application, and the MPD metadata, datadelivered via broadcasting is sent to the broadcast server 20 and datadelivered via communication is sent to the communication server 30.

The Ad/DASH server 10 is configured as described above.

(Configuration of Broadcast Server)

FIG. 23 is a diagram illustrating a configuration example of thebroadcast server 20 depicted in FIG. 1.

In FIG. 23, the broadcast server 20 includes a reception section 201, asignaling generation section 202, a processing section 203, and atransmission section 204.

The reception section 201 receives the Ad segment and the DASH segment,the script application, and the MPD metadata, sent from the Ad/DASHserver 10 and supplies them to the processing section 203. It should benoted, however, that, here, not all of the Ad segment and the DASHsegment, the script application, and the MPD metadata are necessarilyprovided from the Ad/DASH server 10 and that only data (files) deliveredvia broadcasting is provided to and received by the reception section201.

Also, the reception section 201 receives NRT content data (files) froman external server (not depicted) and supplies it to the processingsection 203.

The signaling generation section 202 generates signaling and supplies itto the processing section 203. Here, signaling includes LLS signalingsuch as SLT metadata and SLS signaling such as USBD metadata, S-TSIDmetadata, and AST metadata. Also, in a case where a resource (file) isshared among a plurality of services, a quota domain identifier of atarget cache quota domain is specified in the quotaDomain attributedefined in SLT metadata, USBD metadata, S-TSID metadata, or ASTmetadata.

The processing section 203 performs necessary processes on the Adsegment and the DASH segment, the script application, the MPD metadata,and the NRT content supplied from the reception section 201 and thesignaling supplied from the signaling generation section 202 andsupplies the data to the transmission section 204. Here, for example,processes for generating an IP/UDP packet containing, in a payload, LCTsession data including the Ad segment and the DASH segment, the scriptapplication, the NRT content, and the SLS signaling (e.g., USBD metadataand MPD metadata) and an IP/UDP packet containing LLS signaling (e.g.,SLT metadata) data in a payload, are performed.

The transmission section 204 sends (broadcasts) a broadcast wave(digital broadcast signal) for data supplied from the processing section203 using an antenna 211 via the transport channel 80.

The broadcast server 20 is configured as described above.

(Configuration of Communication Server)

FIG. 24 is a diagram illustrating a configuration example of thecommunication server 30 depicted in FIG. 1.

In FIG. 24, the communication server 30 includes a reception section301, a period file generation section 302, a processing section 303, anda communication section 304.

The reception section 301 receives the Ad segment and the DASH segment,the script application, and the MPD metadata, sent from the Ad/DASHserver 10, and supplies them to the processing section 303. It should benoted, however, that, here, not all of the Ad segment and the DASHsegment, the script application, and the MPD metadata are necessarilyprovided from the Ad/DASH server 10 and that only data (files) deliveredvia communication is provided to and received by the reception section301.

The processing section 303 processes the data supplied from thereception section 301 in response to a request (XLink resolutionrequest) from the client apparatus 40 received by the communicationsection 304 and supplies resultant data to the communication section304. The communication section 304 sends, in response to a request fromthe client apparatus 40, the data (at least one of the Ad segment andthe DASH segment, the script application, and the MPD metadata),supplied from the processing section 303, addressed to the clientapparatus 40, the requester of the data, via the Internet 90.

The processing section 303 requests the period file generation section302 to generate a period file in response to a request from the clientapparatus 40 received from the communication section 304. The periodfile generation section 302 generates a period file including the Periodelement tailored to the user (user's characteristic) using the clientapparatus 40 in response to the request from the processing section 303and supplies the period file to the processing section 303.

The processing section 303 processes the period file supplied from theperiod file generation section 302 and supplies the file to thecommunication section 304. The communication section 304 sends theperiod file, supplied from the processing section 303, addressed to theclient apparatus 40, the requester of the XLink resolution request, viathe Internet 90.

The communication server 30 is configured as described above.

(Configuration of Client Apparatus)

FIG. 25 is a diagram illustrating a configuration example of the clientapparatus 40 depicted in FIG. 1.

In FIG. 25, the client apparatus 40 includes a control section 401, areception section 402, broadcast middleware 403, a local cache 404, abrowser 405, an output section 406, and a communication section 407.

The control section 401 controls the operation of the respectivesections of the client apparatus 40.

The reception section 402 receives and processes the broadcast wave(digital broadcast signal) sent (broadcast) from the broadcast server 20using an antenna 411 via the transport channel 80 and supplies the dataacquired therefrom to the broadcast middleware 403. It should be notedthat the reception section 402 includes, for example, a tuner.

The broadcast middleware 403 processes the data supplied from thereception section 402 and supplies the processed data to the controlsection 401 and the local cache 404. Here, of the data to be processed,the Ad segment and the DASH segment, the script application, and the MPDmetadata are supplied to the local cache 404. Also, the signaling issupplied to the control section 401.

The control section 401 includes a cache control section 401A and areproduction control section 401B. The cache control section 401Acontrols the local cache 404 on the basis of signaling supplied from thebroadcast middleware 403, a request from the browser 405, and so on.Also, the reproduction control section 401B controls the browser 405 onthe basis of signaling supplied from the broadcast middleware 403 and soon.

The local cache 404 is realized on an On Memory, SSD (Solid StateDrive), or other local file system, for example.

The local cache 404 caches data (files) supplied from the broadcastmiddleware 403 under control of the cache control section 401A. Datasuch as Ad segment and DASH segment, script application, and MPDmetadata is cached in the local cache 404. Also, the local cache 404includes a normal cache 404A and a persistent cache 404B.

Here, the normal cache 404A is a normal cache, and data cached thereinis deleted after an appropriate amount of time (a not-so-long timeperiod) elapses. On the other hand, the persistent cache 404B is aspecial cache, and data cached therein has preferential persistence andremains cached for a longer time period than data cached in the normalcache 404A.

Where a quota domain identifier (of the cache quota domain) is specifiedin the signaling (quotaDomain attribute defined in the SLT metadata,USBD metadata, S-TSID metadata, or AST metadata included in thesignaling) from the broadcast middleware 403, and when a request is madefrom the browser 405 (script execution section 405A of the browser 405)to pull the target Ad segment and DASH segment and so on into thepersistent cache 404B, the cache control section 401A pulls the targetAd segment and DASH segment and so on (the files thereof) into thepersistent cache 404B.

As a result, a group of files such as Ad segment and DASH segment cachedin the persistent cache 404B are linked by the quota domain identifier.As a result, a file such as Ad segment or DASH segment is shared among aplurality of services that belong to the same cache quota domain.

The browser 405 is a browser that supports HTML5, JavaScript (registeredtrademark), and so on. The browser 405 processes data (files) read fromthe local cache 404 under control of the reproduction control section401B. The browser 405 includes the script execution section 405A and aDASH client 405B.

The script execution section 405A can execute a script written in ascript language such as JavaScript (registered trademark). For example,the script execution section 405A can read a script application from thelocal cache 404 (the normal cache 404A or the persistent cache 404Bthereof) and execute the application.

Also, the script execution section 405A causes the cache control section401A to control the local cache 404 by executing the CacheStorage API(Application Programming Interface) written in the script application.It should be noted that the detailed content of this CacheStorage APIwill be described later. Further, the script execution section 405Agenerates a period file that matches user preference and so on inresponse to an XLink resolution request from the DASH client 405B andsends the file to the DASH client 405B as a response.

The DASH client 405B reads the MPD metadata (file thereof) from thelocal cache 404 (normal cache 404A thereof) and parses the MPD metadata(analyzes the syntax thereof). In accordance with the result of analyzesof the MPD metadata, the DASH client 405B reads the Ad segment or theDASH segment (file thereof) from the local cache 404 (normal cache 404Aor persistent cache 404B thereof) and reproduces the segment.

The data of the Ad segment or the DASH segment reproduced by the DASHclient 405B is supplied to the output section 406. The output section406 outputs the data supplied from the DASH client 405B under control ofthe reproduction control section 401B. As a result, a broadcast program,an advertisement, or other content is reproduced, and its video andaudio are output.

The communication section 407 exchanges data with the communicationserver 30 via the Internet 90 under control of the control section 401.Of the data received by the communication section 407, the Ad segmentand the DASH segment, the script application, and the MPD metadata aresupplied to the local cache 404. Also, the signaling is supplied to thecontrol section 401. Processes performed on these pieces of dataacquired via communication are similarly to those described above forthe data acquired via broadcasting. Therefore, the description thereofis omitted.

The client apparatus 40 is configured as described above.

6. Flow of Processes Performed by Each Apparatus

A description will be given next of a flow of processes handled by eachapparatus of the transport system 1 depicted in FIG. 1 with reference tothe flowcharts depicted in FIGS. 26 to 28.

(Flow of Processes on Transmitting Side)

A description will be given first of a flow of processes on atransmitting side performed by the Ad/DASH server 10, the broadcastserver 20, and the communication server 30 with reference to theflowchart depicted in FIG. 26.

It should be noted that, in FIG. 26, the processes from step S101 tostep S106 are performed by the Ad/DASH server 10, the processes fromstep S201 to step S205 are performed by the broadcast server 20, and theprocesses in steps S301 and S302 are performed by the communicationserver 30.

In step S101, the Ad/DASH segment generation section 102 of the Ad/DASHserver 10 generates an Ad segment and a DASH segment. Also, in stepS102, the transmission section 106 of the Ad/DASH server 10 sends the Adsegment and the DASH segment generated by the process in step S101 tothe broadcast server 20.

Here, the Ad segment is a segment file acquired by processingadvertisement content. Also, the DASH segment is a segment file acquiredby processing broadcast program content. A description will be givenhere of a case in which an Ad segment and a DASH segment are generatedat the same time for reasons of description. However, these segments maybe generated at different times.

In step S201, the signaling generation section 202 of the broadcastserver 20 generates signaling. In step S202, the transmission section204 of the broadcast server 20 sends (broadcasts) the signalinggenerated by the process in step S201 via the transport channel 80.

Here, LLS signaling such as SLT metadata and SLS signaling such as USBDmetadata are generated as signaling. Also, in a case where a resource(file) is shared among a plurality of services, a quota domainidentifier of a target cache quota domain is specified in thequotaDomain attribute defined in SLT metadata, USBD metadata, S-TSIDmetadata, or AST metadata.

Also, in the broadcast server 20, the Ad segment and the DASH segmentsent by the process in step S202 are received by the reception section201. Then, in step S203, the transmission section 204 of the broadcastserver 20 sends (broadcasts) the Ad segment and the DASH segmentgenerated by the Ad/DASH server 10 via the transport channel 80.

In step S103, the script application generation section 103 of theAd/DASH server 10 generates a script application. In step S104, thetransmission section 106 of the Ad/DASH server 10 sends the scriptapplication generated by the process in step S103 to the broadcastserver 20.

In the broadcast server 20, the script application sent by the processin step S104 is received by the reception section 201. Then, in stepS204, the transmission section 204 of the broadcast server 20 sends(broadcasts) the script application generated by the Ad/DASH server 10via the transport channel 80.

In step S105, the MPD generation section 104 of the Ad/DASH server 10generates MPD metadata. In step S106, the transmission section 106 ofthe Ad/DASH server 10 sends the MPD metadata generated by the process instep S105 to the broadcast server 20.

Here, Period elements of a broadcast program and an advertisement arewritten in the MPD metadata. In the Period element of the advertisement,for example, the URL “urn:atsc:ad-insertion:abc:1234” is written as thexlink:href attribute. It should be noted, however,“urn:atsc:ad-insertion” in this URL indicates that a request must bemade to the script (script application) executed locally (by the clientapparatus 40) to resolve ad-insertion control.

That is, according to MPEG-DASH rules, by writing a URL made up of acharacter string starting with normal “http:” in the xlink:hrefattribute of the Period element in MPD metadata, the client apparatus 40inquires the communication server 30 on the Internet 90 specified bythis “http: . . . .” Then, the client apparatus 40 receives a periodfile as a response from the communication server 30 and reproducesadvertisement content (Ad segment) on the basis of the content of thePeriod element included in the period file.

In this example, on the other hand, a URN (Uniform Resource Name) madeup of a character string starting with “urn:atsc:ad-insertion” iswritten in the xlink:href attribute of the Period element of MPDmetadata rather than a URL made up of a character string starting with“http:.” As a result, in a case where the Period element having thexlink:href attribute with a character string starting with“urn:atsc:ad-insertion” specified therein is detected in the clientapparatus 40 during parsing (analyzing the syntax) of MPD metadata, anevent rather than an HTTP request is issued to the script applicationthat is executed at the same time to prompt XLink resolution (Periodelement resolution).

It should be noted that although a case will be mainly described in thisexample in which a URN made up of a character string starting with“urn:atsc:ad-insertion” is specified in the xlink:href attribute of thePeriod element in MPD metadata, a URL such as“http://adservice.com/adp-1?user=$groupID$” is specified as describedabove so that a specific user is specified by a groupID.

In the broadcast server 20, the MPD metadata sent by the process in stepS106 is received by the reception section 201. Then, in step S205, thetransmission section 204 of the broadcast server 20 sends (broadcasts)the MPD metadata generated by the Ad/DASH server 10 via the transportchannel 80.

It should be noted that, for reasons of description, in step S202 tostep S205, a description was given assuming that signaling, an Adsegment and a DASH segment, a script application, and MPD metadata aresent at different times, these pieces of data are sent included in abroadcast stream.

In the communication server 30, an XLink resolution request sent fromthe client apparatus 40 via the Internet 90 is received by thecommunication section 304. Then, in step S301, the period filegeneration section 302 of the communication server 30 generates a periodfile. In step S302, the communication section 304 of the communicationserver 30 sends the period file generated by the process in step S301addressed to the client apparatus 40, the sender of the XLink resolutionrequest, via the Internet 90.

It should be noted that an XLink resolution request is sent from theclient apparatus 40 to the communication server 30 as described abovewhere a URL made up of a character string starting with “http:” iswritten in the xlink:href attribute of the Period element in MPDmetadata.

Hitherto, a description has been given of the flow of processes on thetransmitting side.

(Flow of Processes on Receiving Side)

A description will be given next of a flow of processes performed by theclient apparatus 40 on the receiving side with reference to theflowcharts depicted in FIGS. 27 and 28.

It should be noted that, in FIGS. 27 and 28, the processes from stepS401 to step S408 are performed by the broadcast middleware 403 and theprocesses from step S421 to step S423 and the processes from step S441to step S443 are performed by the cache control section 401A thatcontrols the local cache 404 (normal cache 404A or persistent cache404B). Also, the processes from step S461 to step S466 are performed bythe script execution section 405A of the browser 405, and the processesfrom step S481 to step S490 are performed by the DASH client 405B of thebrowser 405.

In step S401, the broadcast middleware 403 receives, via the receptionsection 402, signaling sent from the broadcast server 20 via thetransport channel 80. In step S402, the broadcast middleware 403processes the signaling received by the process in step S401.

Here, LLS signaling such as SLT metadata and SLS signaling such as USBDmetadata are processed as signaling. Also, in a case where a resource(file) is shared among a plurality of services, a quota domainidentifier of a target cache quota domain is specified in thequotaDomain attribute defined in SLT metadata, USBD metadata, S-TSIDmetadata, or AST metadata, thereby allowing the services that belong tothis cache quota domain to be recognized.

In step S403, the broadcast middleware 403 receives, via the receptionsection 402, an Ad segment and a DASH segment sent from the broadcastserver 20 via the transport channel 80. In step S404, the broadcastmiddleware 403 transports the Ad segment and the DASH segment, receivedby the process in step S403, to the local cache 404.

In step S421, the cache control section 401A caches the Ad segment andthe DASH segment (files thereof), transported by the process in stepS404, in the normal cache 404A of the local cache 404.

In this case, the Ad segment and the DASH segment (files thereof) arecached in the normal cache 404A. Therefore, if this condition continues,these segments are deleted after an appropriate amount of time (anot-so-long time period) elapses. Also, although a case is describedhere in which the Ad segment and the DASH segment (files thereof) arecached at the same time for reasons of description, these segments(files thereof) may be cached at different times.

In step S405, the broadcast middleware 403 receives, via the receptionsection 402, a script application sent from the broadcast server 20 viathe transport channel 80. In step S406, the broadcast middleware 403transports the script application, received by the process in step S405,to the local cache 404.

In step S422, the cache control section 401A caches the scriptapplication, transported by the process in step S406, in the normalcache 404A of the local cache 404. In this case, the script applicationis cached in the normal cache 404A. Therefore, if this conditioncontinues, the script application is deleted after an appropriate amountof time (a not-so-long time period) elapses.

In step S461, the script execution section 405A acquires the scriptapplication, cached in the normal cache 404A by the process in stepS422, from the local cache 404 and executes the script application.

In step S462, the script execution section 405A requests the cachecontrol section 401A to pull the Ad segment into the persistent cache404B in response to the execution of the script application (process instep S461).

Here, the instruction to pull the Ad segment into the persistent cache404B takes place, for example, as the following CacheStorage API,written in the script application, is executed:

Interface Cache { Promise<void> fetchPeriod(xmlElement); }

It should be noted, however, that, in the above API, the fetchPeriodmethod is used to instruct that pulling into the persistent cache 404Btake place. Also, the segment file (Ad segment file) specified by thesegment URL written in the Period element specified by xmlElement, theargument of the fetchPeriod method, is the file stored in the persistentcache 404B.

Also, the following CacheStorage API may be written in the scriptapplication:

Interface Cache { Promise<void> fetchFile(url); }

It should be noted, however, that, in the above API, the fetchFilemethod is used to instruct that pulling into the persistent cache 404Btake place. Also, the segment file (Ad segment file) specified by theurl, the argument of the fetchFile method, is the file stored in thepersistent cache 404B.

In step S441, the cache control section 401A pulls the Ad segment (filethereof), a potential insertion segment, from the normal cache 404A ofthe local cache 404 into the persistent cache 404B in response to thepull request made by the process in step S462. As a result, the Adsegment (file thereof), pulled from the normal cache 404A, is cached inthe persistent cache 404B of the local cache 404 (S442).

That is, a group of files delivered by way of broadcasting via thetransport channel 80 are loaded into the normal cache 404A (HTTP proxycache (file system)) of the local cache 404 after the ROUTE protocol isterminated by the broadcast middleware 403 and deleted after anappropriate amount of time (a not-so-long time period) elapses. Here,for example, the files are deleted after the amount of time determinedby a cache expiration time written in an HTTP header added at the timeof file transport in ROUTE entity mode and so on.

On the other hand, the persistent cache 404B of the local cache 404 is acache treated as a special area of the HTTP proxy cache. That is, agroup of files loaded into the persistent cache 404B have morepreferential persistence than a group of other files cached in thenormal cache 404A. Further, the files are not deleted even after theabove “appropriate amount of time” elapses and remain cached until thequota allocated to the local cache 404 is reached.

Then, services to which the group of files cached in the persistentcache 404B belong are linked by the quota domain identifier specified bythe quotaDomain attribute defined in SLT metadata, USBD metadata, S-TSIDmetadata, or AST metadata. As a result, a specific file (Ad segment filein this example) is shared among a plurality of services that belong tothe same cache quota domain.

In step S407, the broadcast middleware 403 receives, via the receptionsection 402, MPD metadata sent from the broadcast server 20 via thetransport channel 80. In step S408, the broadcast middleware 403transports the MPD metadata, received by the process in step S407, tothe local cache 404.

In step S423, the cache control section 401A caches the MPD metadata,transported by the process in step S408, in the normal cache 404A of thelocal cache 404. In this case, the MPD metadata is cached in the normalcache 404A. Therefore, the MPD metadata is deleted after an appropriateamount of time (a not-so-long time period) elapses.

In step S481, the DASH client 405B acquires the MPD metadata, cached inthe normal cache 404A by the process in step S423, from the local cache404 and parses the MPD metadata (analyzes the syntax thereof).

In step S482, the DASH client 405B acquires, from the local cache 404,the DASH segment acquired in response to the result of the process instep S402 or S481 (processing result of SLT, USBD, S-TSID, MPD, or othermetadata) and cached in the normal cache 404A. In step S483, the DASHclient 405B reproduces the DASH segment acquired by the process in stepS482 under control of the reproduction control section 401B. As aresult, the broadcast program content is reproduced in the clientapparatus 40.

In step S484, the DASH client 405B determines whether to insert anadvertisement. Where it is determined in step S484 that an advertisementis not inserted, the process returns to step S482, and the processesfrom step S482 to step S484 are repeated. In this case, the reproductionof the broadcast program content continues. On the other hand, where itis determined that an advertisement is inserted in step S484, theprocess proceeds to step S485.

In step S485, the DASH client 405B requests the script execution section405A to resolve XLink included in the MPD metadata in response to theresult of the process in step S481.

It should be noted, however, that where a URN made up of a characterstring starting with “urn:atsc:ad-insertion” is detected from the URLspecified by the xlink:href attribute of the Period element of the MPDmetadata by the process in step S481, an event is issued to the scriptapplication that is executed by the script execution section 405A at thesame time to prompt XLink resolution (Period element resolution).

In step S463, the script execution section 405A acquires a userpreference using a logic in the script of the script application beingexecuted in response to the XLink resolution request made by the processin step S485. Then, in step S464, the script execution section 405Agenerates a period file on the basis of the user preference acquired bythe process in step S463.

Here, the script execution section 405A generates a period file thatincludes the Period element to be inserted into MPD metadata on thebasis of the URL (e.g., URL such as “urn:atsc:ad-insertion:abc:1234”)notified by an event from the DASH client 405B. It should be noted thatPDI (Preference Demographic and Interest), for example, may be used as auser preference. This PDI is a mechanism that ensures reproduction(accumulation) of only content that matches user's preferences bygenerating information indicating the user's answer to the questionprovided by a specific server.

In step S465, the script execution section 405A sends the period file,generated by the process in step S464, to the DASH client 405B as aresponse.

It should be noted that where a URL made up of a character stringstarting with “http:” (e.g., URL such as“http://adservice.com/adp-1?user=$groupID$”) is written in thexlink:href attribute of the Period element in MPD metadata, an XLinkresolution request is sent to the communication server 30 via theInternet 90 as depicted by a dotted line in the figure (dotted line“5”). Then, the period file appropriate to the XLink resolution requestsent from the communication server 30 is acquired as depicted by adotted line in the figure (dotted line “6”).

In step S486, the DASH client 405B acquires the period file sent as aresponse by the process in step S465 and parses the period file(analyzes the syntax thereof).

In step S487, the DASH client 405B acquires the Ad segment cached in thepersistent cache 404B of the local cache 404 in response to the resultof the process in step S486. Here, the URL of the target Ad segment isacquired by the process in step S486 as a result of parsing of thePeriod element, and the Ad segment in the persistent cache 404B isacquired in accordance with the URL. Then, the file of this Ad segmentis a file shared among a plurality of services that belong to the samecache quota domain. Therefore, the Ad segment file can be reused.

In step S488, the DASH client 405B reproduces the Ad segment, acquiredby the process in step S487, under control of the reproduction controlsection 401B. As a result, in the client apparatus 40, content to bereproduced is switched from a broadcast program to an advertisement(advertisement is inserted).

In step S489, the DASH client 405B determines whether the reproductionof the Ad segment (process in step S488) is complete. Where it isdetermined in step S489 that the Ad segment reproduction has yet to becomplete, the process returns to step S488, and the Ad segmentreproduction continues.

On the other hand, where it is determined in step S489 that the Adsegment reproduction is complete, the process proceeds to step S490. Instep S490, the DASH client 405B notifies the script execution section405A that the Ad segment reproduction is complete.

In step S466, the script execution section 405A requests the cachecontrol section 401A to delete the Ad segment whose reproduction iscomplete from the persistent cache 404B using the script applicationbeing executed in response to the notification regarding the completionof the Ad segment reproduction made in step S490.

Here, an instruction to delete the Ad segment from the persistent cache404B is made, for example, by executing the following CacheStorage APIwritten in the script application:

Interface Cache { Promise<void> deleteFile(url); }

It should be noted, however, that, in the above API, the deleteFilemethod is used to instruct that deletion from the persistent cache 404Btake place. Also, the segment file (Ad segment file) specified by theurl, the argument of the deleteFile method, is the file deleted from thepersistent cache 404B.

In step S443, the cache control section 401A deletes the Ad segment(file thereof) whose reproduction is complete from the persistent cache404B of the local cache 404 in response to the deletion request made bythe process in step S466. It should be noted that, in the clientapparatus 40, content to be reproduced is switched from an advertisementto a broadcast program when the Ad segment reproduction ends.

Hitherto, a description has been given of the flow of processes on thereceiving side.

7. Modification Example

Although, in the above description, ATSC (ATSC 3.0 in particular), ascheme employed, for example, in the United States, was described as adigital broadcasting standard, the present technology may be applied toISDB (Integrated Services Digital Broadcasting), a scheme adopted, forexample, in Japan and DVB (Digital Video Broadcasting), a scheme adoptedin European nations, and so on. Also, although, a description was givenin the above description by citing ATSC 3.0 that adopts the IP transportscheme as an example, the transport scheme to which the presenttechnology is applied is not limited to the IP transport scheme, and thepresent technology may be applied to other scheme such as MPEG2-TS(Transport Stream).

Also, the present technology is applicable, among digital broadcasting,not only to terrestrial broadcasting and satellite broadcasting such asbroadcasting satellite (BS) and communications satellite (CS) but alsoto wired broadcasting such as cable television (CATV).

Also, the domain and signaling names described above are merelyexamples, and there are cases in which other names may be used. Itshould be noted, however, that these differences in name are differencesin formality and that there is no difference in substantial content of atarget domain or signaling. For example, cache quota domain may becalled by other name such as cache quota group having a similar nuance.Also, for example, AST (Application Signaling Table) may be referred toas AIT (Application Information Table) and so on, and NRT (Non RealTime) may be referred to as LCC (Locally Cached Content). Further, in acase where signaling is written in a markup language such as XML, thenames of the elements and attributes thereof are merely examples, andother names may be used. It should be noted, however, that thesedifferences in name are differences in formality and that there is nodifference in substantial content of the elements and attributesthereof.

Also, although, in the above description, SLT metadata was described asLLS signaling, metadata such as EAT (Emergency Alerting Table) and RRT(Region Rating Table) may be included in LLS signaling. EAT metadataincludes information related to emergency information that must beannounced urgently. RRT metadata includes information related to rating.

It should be noted that applications are not limited to those developedusing a markup language such as HTML5 or a script language such asJavaScript (registered trademark) and may be applications developedusing a programming language such as Java (registered trademark). Also,any content such as electronic book, game, and music in addition tovideo and advertisement may be included in the content described above.

Also, the present technology is applicable to a given standard (standardother than broadcasting standard) specified on the premise thattransport channels other than broadcasting network, i.e., communicationlines (communication networks) such as the Internet and telephonenetwork, are used as transport channels.

8. Configuration of Computer

The series of processes described above may be performed by hardware orsoftware. In a case where the series of processes are performed bysoftware, the program making up the software is installed to a computer.FIG. 29 is a diagram illustrating a hardware configuration example of acomputer for performing the above series of processes using the program.

In a computer 1000, a CPU (Central Processing Unit) 1001, a ROM (ReadOnly Memory) 1002, and a RAM (Random Access Memory) 1003 are connectedto each other by a bus 1004. An input/output (I/O) interface 1005 isfurther connected to the bus 1004. An input section 1006, an outputsection 1007, a recording section 1008, a communication section 1009,and a drive 1010 are connected to the I/O interface 1005.

The input section 1006 includes a keyboard, a mouse, a microphone, andso on. The output section 1007 includes a display, a speaker, and so on.The recording section 1008 includes a hard disk, a non-volatile memory,and so on. The communication section 1009 includes a network interfaceand so on. The drive 1010 drives a removable medium 1011 such asmagnetic disk, optical disc, magneto-optical disk, or semiconductormemory.

In the computer 1000 configured as described above, the above series ofprocesses are performed as the CPU 1001 loads, for example, the programrecorded in the ROM 1002 or the recording section 1008 into the RAM 1003via the I/O interface 1005 and the bus 1004 for execution.

The program executed by the computer 1000 (CPU 1001) can be providedrecorded, for example, in the removable medium 1011 as a packaged mediumor the like. Alternatively, the program can be provided via a wired orwireless transport medium such as local area network, the Internet, anddigital satellite broadcasting.

In computer 1000, the program can be installed to the recording section1008 via the I/O interface 1005 as the removable medium 1011 is insertedinto the drive 1010. Alternatively, the program can be received by thecommunication section 1009 via a wired or wireless transport medium andinstalled to the recording section 1008. In addition to the above, theprogram can be installed, in advance, to the ROM 1002 or the recordingsection 1008.

Here, in the present specification, the processes performed by thecomputer in accordance with the program need not necessarily beperformed chronologically in accordance with the sequence described as aflowchart. That is, the processes performed by the computer inaccordance with the program include those that are performed in parallelor individually (e.g., parallel processes or object-based processes).Also, the program may be processed by a single computer (processor) orby a plurality of computers in a distributed manner.

It should be noted that embodiments of the present technology are notlimited to those described above and can be modified in various wayswithout departing from the gist of the present technology.

It should be noted that the present technology can have the followingconfigurations:

(1)

A reception apparatus including:

a reception section adapted to receive content; and

a control section adapted to control, on the basis of controlinformation that is transported together with the content and thatincludes resource sharing information indicating whether a resource ofthe content is shared among a plurality of services, storage of theresource in a storage apparatus such that the resource is shared amongthe plurality of services.

(2)

The reception apparatus of feature (1), in which

in a case where the resource sharing information included in the controlinformation indicates that a resource is shared among a plurality ofservices, the control section stores a shared resource that is shared ina manner that distinguishes the shared resource from other resources.

(3)

The reception apparatus of feature (1) or (2), in which

the content and the control information are transported by a broadcastwave,

the services are digital broadcasting services, and

the control information is signaling for providing the services.

(4)

The reception apparatus of feature (3), in which

the signaling is first signaling that permits specification of anattribute for a plurality of services, and

the first signaling includes the resource sharing information specifiedon a service-by-service basis.

(5)

The reception apparatus of feature (3), in which

the signaling is second signaling that permits specification of anattribute for each service, and

the second signaling includes the resource sharing information specifiedin given units within a target service.

(6)

The reception apparatus of feature (5), in which

the resource sharing information is specified on a service-by-service,on a session-by-session, or on an application-by-application basis.

(7)

The reception apparatus of any one of features (2) to (6), in which

the content resource is a file in given format, and

the control section stores a shared resource file in a second storagearea different from a first storage area where other resource files arestored in response to operation of an application transported togetherwith the content.

(8)

The reception apparatus of feature (7), in which

the control section deletes the shared resource file, stored in thesecond storage area, in response to operation of the application.

(9)

The reception apparatus of any one of features (3) to (8), in which

the broadcast wave is a broadcast wave compliant with an IP (InternetProtocol) transport scheme, and

data of the content resource file is placed into an IP packet thatincludes a UDP (User Datagram Protocol) packet and transported.

(10)

The reception apparatus of any one of features (1) to (9), in which

the content includes advertisement content, and

the resource sharing information is identification information foridentifying a group to which a plurality of services sharing a resourceof the advertisement content belong.

(11)

A data processing method of a reception apparatus, the data processingmethod including:

a step in which the reception apparatus receives content and controls,on the basis of control information that is transported together withthe content and that includes resource sharing information indicatingwhether a resource of the content is shared among a plurality ofservices, storage of the resource in a storage apparatus such that theresource is shared among the plurality of services.

(12)

A transmission apparatus including:

a generation section adapted to generate control information thatincludes resource sharing information indicating whether a resource ofcontent is shared among a plurality of services; and

a transmission section adapted to send the control information togetherwith the content.

(13)

The transmission apparatus of feature (12), in which

the content and the control information are transported by a broadcastwave,

the services are digital broadcasting services, and

the control information is signaling for providing the services.

(14)

The transmission apparatus of feature (13), in which

the signaling is first signaling that permits specification of anattribute for a plurality of services, and

the first signaling includes the resource sharing information specifiedon a service-by-service basis.

(15)

The transmission apparatus of feature (13), in which

the signaling is second signaling that permits specification of anattribute for each service, and

the second signaling includes the resource sharing information specifiedin given units within a target service.

(16)

The transmission apparatus of feature (15), in which

the resource sharing information is specified on a service-by-service,on a session-by-session, or on an application-by-application basis.

(17)

The transmission apparatus of any one of features (12) to (16), in whichthe content resource is a file in given format.

(18)

The transmission apparatus of any one of features (13) to (17), in which

the broadcast wave is a broadcast wave compliant with an IP transportscheme, and

data of the content resource file is placed into an IP packet thatincludes a UDP packet and transported.

(19)

The transmission apparatus of any one of features (12) to (18), in which

the content includes advertisement content, and

the resource sharing information is identification information foridentifying a group to which a plurality of services sharing a resourceof the advertisement content belong.

(20)

A data processing method of a transmission apparatus, the dataprocessing method including:

a step in which the transmission apparatus generates control informationthat includes resource sharing information indicating whether a resourceof content is shared among a plurality of services and sends the controlinformation together with the content.

REFERENCE SIGNS LIST

1 Transport system, 10 Ad/DASH server, 20 Broadcast server, 30Communication server, 40 Client apparatus, 80 Transport channel, 90Internet, 101 Reception section, 102 Ad/DASH segment generation section,103 Script application generation section, 104 MPD generation section,105 Processing section, 106 Transmission section, 201 Reception section,202 Signaling generation section, 203 Processing section, 204Transmission section, 301 Reception section, 302 Period file generationsection, 303 Processing section, 304 Communication section, 401 Controlsection, 401A Cache control section, 401B Reproduction control section,402 Reception section, 403 Broadcast middleware, 404 Local cache, 404ANormal cache, 404B Persistent cache, 405 Browser, 405A Script executionsection, 405B DASH client, 406 Output section, 407 Communicationsection, 1000 Computer, 1001 CPU

1. (canceled)
 2. A reception apparatus comprising: reception circuitryconfigured to receive control information and content, the controlinformation including resource sharing information indicating whether aresource is shared among a plurality of applications; and processingcircuitry configured to control, based on the resource sharinginformation, sharing of the resource among the plurality ofapplications, wherein: the resource sharing information includes anidentifier that is associated with the plurality of applications amongwhich the resource is shared, and the resource includes at least onefile associated with at least one of the plurality of applications. 3.The reception apparatus of claim 2, wherein the processing circuitry isconfigured to store the resource in association with the identifier sothat the resource can be accessed by the plurality of applications withwhich the identifier is associated.
 4. The reception apparatus of claim2, wherein at least one of the plurality of applications is a broadcastapplication.
 5. The reception apparatus of claim 2, wherein theprocessing circuitry is configured to control storage of the resourcesuch that the resource is shared among the plurality of applications, inaccordance with the resource sharing information.
 6. The receptionapparatus of claim 2, wherein: the content and the control informationare included in a broadcast signal, and the control information includessignaling for providing digital broadcast services.
 7. The receptionapparatus of claim 2, wherein the control information includesinformation indicating a location of an entry point of at least one ofthe plurality of applications.
 8. The reception apparatus of claim 2,wherein the processing circuitry is configured to store the resource ina first storage area and a further resource of an application associatedwith a further identifier in a second storage area, the second storagearea being different from the first storage area.
 9. The receptionapparatus of claim 8, wherein the processing circuitry is configured toallow the application associated with the further identifier to accessthe further resource in the second storage area and to prevent theapplication associated with the further identifier to access theresource in the first storage area.
 10. The reception apparatus of claim2, wherein the reception circuitry is configured to receive the contentand the control information in a broadcast signal that is compliant withan Internet Protocol (IP) transport scheme.
 11. A non-transitorycomputer-readable medium containing instructions that when executed by aprocessor cause the processor to perform a method comprising: receivingcontrol information and content, the control information includingresource sharing information indicating whether a resource is sharedamong a plurality of applications; and controlling, based on theresource sharing information, sharing of the resource among theplurality of applications, wherein: the resource sharing informationincludes an identifier that is associated with the plurality ofapplications among which the resource is shared, and the resourceincludes at least one file associated with at least one of the pluralityof applications.
 12. A method of a reception apparatus, the methodcomprising: receiving control information and content, the controlinformation including resource sharing information indicating whether aresource is shared among a plurality of applications; and controlling,based on the resource sharing information, sharing of the resource amongthe plurality of applications, wherein: the resource sharing informationincludes an identifier that is associated with the plurality ofapplications among which the resource is shared, and the resourceincludes at least one file associated with at least one of the pluralityof applications.
 13. The method of claim 12 comprising storing theresource in association with the identifier so that the resource can beaccessed by the plurality of applications with which the identifier isassociated.
 14. The method of claim 12, wherein at least one of theplurality of applications is a broadcast application.
 15. The method ofclaim 12 comprising controlling storage of the resource such that theresource is shared among the plurality of applications, in accordancewith the resource sharing information.
 16. The method of claim 12,wherein: the content and the control information are included in abroadcast signal, and the control information includes signaling forproviding digital broadcast services.
 17. The method of claim 12,wherein the control information includes information indicating alocation of an entry point of at least one of the plurality ofapplications.
 18. The method of claim 12 comprising storing the resourcein a first storage area and a further resource of an applicationassociated with a further identifier in a second storage area, thesecond storage area being different from the first storage area.
 19. Themethod of claim 18 comprising allowing the application associated withthe further identifier to access the further resource in the secondstorage area and preventing the application associated with the furtheridentifier to access the resource in the first storage area.
 20. Themethod of claim 12, wherein the content and the control information arereceived in a broadcast signal that is compliant with an InternetProtocol (IP) transport scheme.